Data router connectivity to wireless communication slices

ABSTRACT

A data router serves User Equipment (UEs) over network connections to network slices. The data router receives a container configuration and a connection configuration from a wireless communication network. The data router exchanges user data with the UEs. The data router executes data applications in operating system containers based on the container configuration. The data applications exchange the user data with the network slices over the network connections based on the connection configuration.

RELATED CASES

This United States patent application is a continuation of U.S. patentapplication Ser. No. 17/479,865 that was filed on Sep. 20, 2021 and isentitled “DATA ROUTER CONNECTIVITY TO WIRELESS COMMUNICATION SLICES.”U.S. patent application Ser. No. 17/479,865 is hereby incorporated byreference into this United States patent application.

TECHNICAL BACKGROUND

Wireless communication networks provide wireless data services towireless user devices. Exemplary wireless data services includemachine-control, internet-access, media-streaming, andsocial-networking. Exemplary wireless user devices comprise phones,computers, vehicles, robots, and sensors. The wireless user devicesexecute user applications that use the wireless data services. Forexample, a smartphone may execute a social-networking application thatcommunicates with a content server over a wireless communicationnetwork.

The wireless communication networks have wireless access nodes whichexchange wireless signals with the wireless user devices over radiofrequency bands. The wireless signals use wireless network protocolslike Fifth Generation New Radio (5GNR), Long Term Evolution (LTE),Institute of Electrical and Electronic Engineers (IEEE) 802.11 (WIFI),and Low-Power Wide Area Network (LP-WAN). The wireless access nodesexchange network signaling and user data with network elements that areoften clustered together into wireless network cores.

The wireless network elements comprise Interworking Functions (IWFs),Access and Mobility Management Functions (AMFs), Session ManagementFunctions (SMFs), User Plane Functions (UPFs), and the like. Some of thewireless network elements are grouped into wireless network slices fornetwork services like low-latency remote-computing and high-bandwidthvideo-streaming. The wireless user devices connect to the specificnetwork slices that are specially-purposed for their specific networkservices.

Data routers exchange Internet Protocol (IP) packets to facilitatevarious forms of network communications over both wireless and wirelineconnections. Some data routers directly interface with wireless userdevices over communication protocols like WIFI and 5GNR. The datarouters extend the range of the wireless network services that aredelivered by the wireless communication networks. For example, awireless user device may download video from a wireless network sliceover a WIFI router that is connected to the wireless communicationnetwork over the internet. Unfortunately, the data routers do noteffectively support wireless network slices. Moreover, the data routersdo not efficiently enable the wireless communication networks to controlrouter operations to support the wireless network slices.

TECHNICAL OVERVIEW

In some examples, a data router serves User Equipment (UEs) over networkconnections to network slices. The data router receives a containerconfiguration and a connection configuration from a wirelesscommunication network. The data router exchanges user data with the UEs.The data router executes data applications in operating systemcontainers based on the container configuration. The data applicationsexchange the user data with the network slices over the networkconnections based on the connection configuration.

In some examples, a data router serves UEs over network connections tonetwork slices. The data router comprises a network radio, a user radioand processing circuitry. The network radio receives a containerconfiguration and a connection configuration from a wirelesscommunication network. The user radio exchanges user data with the UEs.The processing circuitry executes data applications in operating systemcontainers based on the container configuration. The data applicationsexchange the user data with the network slices over the network radioand the network connections based on the connection configuration.

DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary wireless communication network that hasa data router to serve User Equipment (UEs) over network connections tonetwork slices.

FIG. 2 illustrates an exemplary operation of the wireless communicationnetwork that has the data router to serve the UEs over the networkconnections to the network slices.

FIG. 3 illustrates an exemplary operation of the wireless communicationnetwork that has the data router to serve the UEs over the networkconnections to the network slices.

FIG. 4 illustrates an exemplary Fifth Generation (5G) wirelesscommunication network that has a wireless router to serve UEs overnetwork connections to network slices.

FIG. 5 illustrates an exemplary UE in the 5G wireless communicationnetwork.

FIG. 6 illustrates an exemplary wireless router in the 5G wirelesscommunication network.

FIG. 7 illustrates exemplary non-3GPP access nodes in the 5G wirelesscommunication network.

FIG. 8 illustrates an exemplary 5G New Radio (5GNR) access node in the5G wireless communication network.

FIG. 9 illustrates an exemplary network data center in the 5G wirelesscommunication network.

FIG. 10 illustrates an exemplary wireless router and Router ControlFunction (RCF) in the 5G wireless communication network.

FIG. 11 illustrates an exemplary operation of the 5G wirelesscommunication network that has the wireless router to serve the UEs overthe network connections to the network slices.

FIG. 12 illustrates an exemplary operation of the 5G wirelesscommunication network that has the wireless router to serve the UEs overthe network connections to the network slices.

FIG. 13 illustrates an exemplary operation of the 5G wirelesscommunication network that has the wireless router to serve the UEs overthe network connections to the network slices.

DETAILED DESCRIPTION

FIG. 1 illustrates an exemplary wireless communication network 100 thathas data router 110 to serve User Equipment (UEs) 101-103 over networkconnections to network slices 132. Wireless communication network 100comprises UEs 101-103, data router 110, access node 120, network control131, and network slices 132. Data router 110 comprises processingcircuitry 111 and memory 112 that are coupled together. UEs 101-103comprise computers, phones, vehicles, sensors, robots, or some otherdata appliances with data communication circuitry. Exemplary wirelessdata services include machine-control, internet-access, media-streaming,social-networking, or some other networking product. Wirelesscommunication network 100 is simplified for clarity and typicallyincludes more UEs, routers, and access nodes than shown.

Various examples of network operation and configuration are describedherein. In some examples, data router 110 stores operating system (OS)116 and router applications (RTR APPs) 117-119 in memory 112. Processingcircuitry 111 retrieves operating system 116 and router applications117-119 from memory 112. Processing circuitry 111 executes operatingsystem 116 to form containers 113-115, and containers 113-115 executerouter applications 117-119 under the control of operating system 116.Router application 119 receives a container configuration, a connectionconfiguration, and a slice configuration from network control 131 overaccess node 120 and router application 118. Router application 119transfers the container configuration to operating system 116. Operatingsystem 116 receives the container configuration from router application119 and controls the processing qualities of containers 113-115 based onthe container configuration from network control 131. Router application117 exchanges user data with UEs 101-103. Router applications 117-118exchange the user data. Router application 118 exchanges the user datawith network slices 132 over network connections through access node 120using service qualities that are indicated in the connectionconfiguration. Router application 118 prioritizes the networkconnections to network slices 132 based on the slice configuration.Router application 119 generates performance information for the networkconnections and transfers the performance information to network control131 over router application 118 and access node 120. Network control 131may modify the container configuration, the connection configuration,and/or the slice configuration for data router 110 based on theperformance information.

In some examples, router application 118 comprises a network applicationthat executes in a network version of container 114, and routerapplication 119 comprises an agent application that executes in agentversion of container 115. The network application in container 114receives the container configuration from network control 131 andtransfers the container configuration to the agent application incontainer 115. The agent application transfers the containerconfiguration to operating system 116. Based on the containerconfiguration, operating system 116 controls Central Processing Unit(CPU) resources, Random Access Memory (RAM), Input/Output (I/O), andother computer resources used by containers 113-115 to executeapplications 117-119. For example, operating system 116 may increase theCPU resources used by containers 113-114 to better support theuser-plane and decrease the CPU resources used by container 115 whichreduces support to the control-plane.

In some examples, router application 118 comprises a network applicationexecuting in a network version of container 114, and router application119 comprises a monitor application executing in a monitor version ofcontainer 115. The network application in container 114 indicates datathroughputs and latencies to the monitor application in container 115.The monitor application receives the data throughputs and latencies fromthe network application and transfers the data throughputs and latenciesto network control 131 over application 118. Network control 131processes the performance data to generate new configurations forcontainers, connections, and slices. Network control 131 transfers thenew configurations to data router 110.

In some examples, router application 118 comprises a network applicationexecuting in network version of container 114, and router application119 comprises a connection application executing in a connection versionof container 115. The connection application in container 115 receivesthe connection configuration from network control 131 over access node120 and the network application in container 114. The connectionapplication may refine the connection configuration based on the currentperformance of router 111. The connection application transfers theconnection configuration to the network application. The networkapplication exchanges user data with network slices 132 over networkconnections using data throughputs and data latencies that are indicatedby the connection configuration. For example, the connectionconfiguration may correlate throughputs for individual UE connections tothe total router throughput to dynamically manage throughput when routerbackhaul quality varies.

In some examples, router application 118 comprises a network applicationexecuting in network version of container 114, and router application119 comprises a slice application executing in a slice version ofcontainer 115. The slice application in container 115 receivesprioritized slice identifiers for UEs 101-103 from network control 131over access node 120 and the network application in container 114. Theslice application transfers the prioritized slice IDs for UEs 101-103 tothe network application. The slice application may refine the sliceconfiguration based on the current performance of router 111. Thenetwork application prioritizes the exchange of user data with networkslices 132 over the network connections based on the prioritized sliceIDs. For example, the slice configuration may correlate slice prioritiesto total router throughput, and some slice IDs may receive a higherpriority when router throughput falls while other slice IDs receive ahigher priority when router throughput bursts.

Advantageously, data router 110 effectively supports network slices 132.Moreover, data router 110 efficiently enables network control 131 tocontrol router operations to support wireless network slices 132.

UEs 101-103 communicate over network connections that are shown in boldand that traverse data router 110, access node 120, and network slices132. The network connections use metallic wiring, glass fibers, radiochannels, or some other communication media. The network connections usetechnologies like Fifth Generation New Radio (5GNR), Long Term Evolution(LTE), Institute of Electrical and Electronic Engineers (IEEE) 802.11(WIFI), Low-Power Wide Area Network (LP-WAN), Bluetooth, IEEE 802.3(ETHERNET), Internet Protocol (IP), Time Division Multiplex (TDM), DataOver Cable System Interface Specification (DOCSIS), General Packet RadioService Transfer Protocol (GTP), virtual switching, inter-processorcommunication, bus interfaces, and/or some other data communicationprotocols. UEs 101-103, data router 110, access node 120, networkcontrol 131, and network slices 132 comprise microprocessors, software,memories, transceivers, bus circuitry, and the like. UEs 101-103, datarouter 110, and access node 120 may include radios, although wirelesscommunications are not required for data router 110. The microprocessorscomprise Digital Signal Processors (DSP), Central Processing Units(CPU), Graphical Processing Units (GPU), Application-Specific IntegratedCircuits (ASIC), and/or the like. The memories comprise Random AccessMemory (RAM), flash circuitry, disk drives, and/or the like. Thememories store software like operating systems, user applications, radioapplications, and network functions. The microprocessors retrieve thesoftware from the memories and execute the software to drive theoperation of wireless communication network 100 as described herein.

FIG. 2 illustrates an exemplary operation of wireless communicationnetwork 100 that has data router 110 to serve UEs 101-103 over thenetwork connections to network slices 132. The operation may differ inother examples. Memory 112 stores operating system 116 and routerapplications 117-119 (201). Processing circuitry 111 executes operatingsystem 116 to form containers 113-115 which execute router applications117-119 (202). Network control 131 transfers a container configuration,a connection configuration, and a slice configuration to router 110 overaccess node 120 (203). Router applications 117-119 receive the containerconfiguration, connection configuration, and slice configuration overaccess node 120 and transfer the container configuration to operatingsystem 116 (204). Operating system 116 receives the containerconfiguration from router application 119 and controls the processingqualities of containers 113-115 based on the container configuration(205). Router applications 117-119 prioritize the network connections tonetwork slices 132 based on the slice configuration (206). Routerapplications 117-118 exchange user data with UEs 101-103 (207). Routerapplications 117-118 exchange the user data with network slices 132 overthe network connections and access node 120 using service qualities fromthe connection configuration (207). Router applications 117-119 generateperformance information for the network connections and transfer theperformance information to network control 131 over access node 120(208). Network control 131 modifies the container configuration, sliceconfiguration, and/or connection configuration based on the performancedata (209). The operation repeats (202).

FIG. 3 illustrates an exemplary operation of wireless communicationnetwork 100 that has data router 110 to serve UEs 101-103 over thenetwork connections to network slices 132. The operation may differ inother examples. Operating system 116 exerts control (CNT) overcontainers 113-115 based on a container configuration. Routerapplications 118-119 exchange signaling (SIG) to establish routerconnectivity to slices 132. Router application 119 and network control131 exchange signaling over access node 120 to establish the routerconnectivity to slices 132. Network control 131 and network slices 132exchange signaling to establish the router connectivity to slices 132.UEs 101-103 and router application 117 exchange signaling to establishrouter connectivity to UEs 101-103. Router applications 117 and 119exchange signaling to initiate UE slice selection. Router application117 and UEs 101-103 exchange signaling to perform UE slice selection.Router applications 118-119 exchange signaling to establish networkconnections for the selected slices. Router application 118 and networkcontrol 131 exchange signaling over access node 120 to establish networkconnections between UEs 101-103 and network slices 132 per the UE slicerequests. UEs 101-103 exchange user data with external systems overrouter applications 117-118, access node 120, and network slices 132 perthe UE slice requests.

Router applications 117-118 generate performance data for the user dataexchanges like throughput, latency, and error rate on a per-UE,per-slice, and per-connection basis. Router applications 117-118transfer the performance data to router application 119 which transfersthe performance data to network control 131 over application 118 andaccess node 120. Network control 131 processes the performance data togenerate configurations for router 110 to control containers 113-115,network connections, and network slices 132. Network control 131transfers the configurations to router application 119 over access node120 and application 118. Router application 119 transfers the containerconfiguration to operating system 116. Router application 119 refinesand transfers the slice and connection configurations to routerapplication 118.

Operating system 116 exerts control over containers 113-115 based on themodified container configuration. For example, operating system 116 mayincrease CPU and RAM resources for a container that supports awork-related services during working hours while reducing CPU and RAMresources for containers that support entertainment-related servicesduring working hours. Operating system 116 may eliminate CPU and RAMresources for a container that supports a redundant service. Routerapplications 118-119 and network control 131 exchange signaling tomodify UE connectivity to network slices 132 based on modified slice andconnection configurations. Router application 117 and UEs 101-103exchange signaling to perform additional slice selection/deselectionbased on modified slice configurations. UEs 101-103 exchange user datawith external systems over router applications 117-118, access node 120,and network slices 132 per the UE slice requests and the configurationsfor container, slice, and connection.

FIG. 4 illustrates an exemplary Fifth Generation (5G) wirelesscommunication network 400 that has wireless router 410 to serve UEs401-403 over network connections to network slices 442-444. 5G wirelesscommunication network 400 comprises an example of wireless communicationnetwork 100, although network 100 may differ. 5G wireless communicationnetwork 400 comprises: UEs 401-403, wireless router (RTR) 410, 5GNRAccess Node (AN) 421, WIFI AN 422, Ethernet (ENET) AN 423, and networkdata center 430. Network data center 430 comprises non-Third GenerationPartnership Project (non-3GPP) Interworking Function (IWF) 431, Accessand Mobility Management Function (AMF) 432, Network Slice SelectionFunction (NSSF) 433, Session Management Function (SMF) 434, and wirelessnetwork slices 441-444. Wireless network slice 441 comprises User PlaneFunction (UPF) 451 and Router Control Function (RCF) 455. Wirelessnetwork slice 442 comprises UPF 452. Wireless network slice 443comprises UPF 453. Wireless network slice 444 comprises UPF 453 andApplication Server Function (ASF) 456.

Router 410 registers with AMF 432 over at least one of: 5GNR AN 421,WIFI AN 422-IWF 431, and ENET AN 423-IWF 431. Router 410 reports arouter capability for slice 441. AMF 432 and NSSF 433 interact toauthorize slice 441 for router 410. AMF 432 signals SMF 434 to connectrouter 410 to slice 441, and SMF 434 configures UPF 451 to serve router410. AMF 432 signals 5GNR AN 421 and/or IWF 431 to connect router 410 toUPF 451. Router 410 registers with RCF 455 over UPF 451. RCF 455transfers a container configuration and slice information to router 410.Router 410 executes router applications in containers based on thecontainer configuration from RCF 455. For example, RCF 455 may increaseCPU and RAM resources for a container that supports a work-relatedservices during working hours while reducing CPU and RAM resources forcontainers that support entertainment-related services during workinghours. RCF 455 may eliminate CPU and RAM resources for a container thatsupports a redundant service.

UE 401 connects to router 410. Router 410 transfers the sliceinformation from RCF 455 to UE 401. UE 401 requests slice 444. Router410 reports a UE capability for slice 444. AMF 432 and NSSF 433 interactto authorize slice 444 for UE 401 over router 410. AMF 432 signals SMF434 to connect router 410 to slice 444, and SMF 434 configures UPF 454to serve router 410 and UE 401. AMF 432 signals 5GNR AN 421 and/or IWF431 to connect router 410 to UPF 454 for UE 401. UE 401 and ASF 456communicate to deliver a data service like augmented-reality.

Router 410 monitors data communication performance and transferscorresponding performance data to RCF 455. RCF 455 processes theperformance data to determine a container configuration, sliceconfiguration and connection configuration. The container configurationindicates computer resource levels for containers (and their routerapplications) based on the current performance and UE slice usage. Theslice configuration indicates slice priorities for slices 441 and 444based on the current performance and UE slice usage. The connectionconfiguration indicates router throughputs between router 410 and slice441 and between UE 401 and slice 444. Router 410 executes the routerapplications in the containers based on the container configuration fromRCF 455. Router 410 prioritizes slices 441 and 444 based on the sliceconfiguration by serving the higher-priority slice before serving thelower-priority slice. Router 410 exchanges data for slice 444 with UE401. Router 410 exchanges data for slices 441 and 444 with one or moreof ANs 421-423 based on the connection throughputs from the connectionconfiguration.

UE 402 connects to router 410. Router 410 transfers the sliceinformation to UE 402. UE 402 requests slices 442 and 444. Router 410reports a UE capability for slices 442 and 444. AMF 432 and NSSF 433authorize slices 442 and 444 for UE 402 over router 410. AMF 432 signalsSMF 434 to connect router 410 to slices 442 and 444, and SMF 434configures UPFs 452 and 454 to serve router 410 and UE 402. AMF 432signals 5GNR AN 421 and/or IWF 431 to connect router 410 to UPFs 452 and454 for UE 402. UE 402 and UPF 452 communicate to deliver the dataservice from slice 442. UE 402 and ASF 456 communicate to deliver thedata service from slice 444.

Router 410 monitors data communication performance and transferscorresponding performance data to RCF 455. RCF 455 processes theperformance data to determine a container configuration, sliceconfiguration, and connection configuration. The container configurationindicates computer resource levels for router applications based on thecurrent performance and UE slice usage. The slice configurationindicates slice priorities for slices 441, 442, and 444 based on thecurrent performance and UE slice usage. The connection configurationindicates router throughputs between router 410 and slice 441, UE 401and slice 444, UE 402 and slice 442, and UE 402 and slice 444. Theconnection configuration indicates a connection priority for the twoslice 444 connections for UEs 401-402 to control which UE is served withthe higher priority (served first) for slice 444. Router 410 executesthe router applications in the containers based on the containerconfiguration from RCF 455. Router 410 prioritizes slices 441, 442, and444 based on the slice configuration by serving the higher-priorityslices before serving the lower-priority slices. Router 410 exchangesdata for slice 444 with UEs 401-402. Router 410 exchanges data forslices 441, 442, and 444 with one or more of ANs 421-423 based on theslice priorities, connection throughputs, and connection priorities fromthe slice and connection configurations.

UE 403 connects to router 410. For UE 403, router 410 selects slices 443and 444 for UE 403 in response to the UE 403 connection. Router 410reports a UE capability for slices 443 and 444. AMF 432 and NSSF 433authorize slices 443 and 444 for UE 403 over router 410. AMF 432 signalsSMF 434 to connect router 410 to slices 443 and 444, and SMF 434configures UPFs 453-454 to serve router 410 and UE 403. AMF 432 signals5GNR AN 421 and/or IWF 431 to connect router 410 to UPFs 453-454 for UE403. UE 403 and UPF 453 communicate to deliver the data service fromslice 443. UE 403 and ASF 456 communicate to deliver the data servicefrom slice 444.

Router 410 monitors data communication performance and transferscorresponding performance data to RCF 455. RCF 455 processes theperformance data to modify the container configuration, sliceconfiguration, and/or connection configuration. The containerconfiguration may be used to allocate router resources among UEs 401-403and slices 441-444. The slice configuration indicates slice prioritiesfor slices 441-444 based on the current performance and UE slice usage.The connection configuration indicates router throughputs between router410 and slice 441, UE 401 and slice 444, UE 402 and slice 442, UE 402and slice 444, UE 403 and slice 443, and UE 403 and slice 444. Theconnection configuration indicates connection priority for the threeconnections for UEs 401-403 in slice 444 to control which UE is servedfirst, second, and third. Router 410 executes the router applications inthe containers based on the container configuration from RCF 455. Router410 prioritizes slices 441-444 based on the slice configuration. Router410 exchanges data for slice 444 with UEs 401-403. Router 410 exchangesdata for slices 441-444 with one or more of ANs 421-423 based on theslice priorities, connection throughputs, and connection priorities fromthe slice and connection configurations.

When the performance of a given slice or UE connection falls, RCF 455may allocate more router resources to the containers that support theslice or connection. Alternatively, RCF 455 may deallocate routerresources from containers that support a poorly performing slice orconnection. When new UEs attach and use slices, RCF 455 may allocatemore router resources to the containers that support the heavily usedslices or connections. RCF 455 may deallocate router resources away fromcontainers that support underused slices or connections. In some cases,UEs 401-403 interact directly with AMF 432 over router 410 to performslice selection. Router 410 reports these UEs and slices to RCF 455. RCF455 processes this slice information to determine the container, slice,and connections configurations.

FIG. 5 illustrates exemplary UE 401 in 5G wireless communication network400. UE 401 comprises an example of UEs 101-102 and 402-403, althoughthese UEs may differ. UE 401 comprises 5GNR radio 501, WIFI radio 502,Ethernet (ENET) card 503, user circuitry 504, and user components 505.User components 505 comprise sensors, controllers, displays, or someother user apparatus that generates slice data. Radios 501-502 compriseantennas, amplifiers, filters, modulation, analog-to-digital interfaces,DSP, memory, and transceivers that are coupled over bus circuitry. ENETcard 503 comprises ports, analog-to-digital interfaces, DSP, memory, andtransceivers that are coupled over bus circuitry. User circuitry 504comprises memory, CPU, user interfaces and components, and transceiversthat are coupled over bus circuitry. The memory in user circuitry 504stores an operating system (OS), user applications (APP), and networkapplications for WIFI, ENET, 5GNR, and IP. The antennas in 5GNR radio501 are wirelessly coupled to router 410 over a 5GNR link. The antennasin WIFI radio 502 are wirelessly coupled to router 410 over a WIFI link.The port in ENET card 503 is wireline coupled to router 410 over anEthernet link. Transceivers (XCVRs) in radios 501-502 and card 503 arecoupled to transceivers in user circuitry 504. Transceivers in usercircuitry 504 are coupled to user components 505. The CPU in usercircuitry 504 executes the operating system, user applications, andnetwork applications to exchange network signaling and user data withrouter 410 over radios 501-502 and/or card 503.

In some examples, some of the 5GNR, WIFI, and ENET components could beomitted. For example, the 5GNR and ENET portions could be omitted toform a WIFI-only UE. The 5GNR and WIFI portions could be omitted to forman ENET-only UE. The WIFI and ENET portions could be omitted to form a5GNR-only UE. Other device combinations could be used like 5GNR/WIFI,5GNR/ENET, and WIFI/ENET.

FIG. 6 illustrates exemplary wireless router 410 in 5G wirelesscommunication network 400. Wireless router 410 comprises an example ofdata router 110, although router 110 may differ. Wireless router 410comprises 5GNR radios 601-602, WIFI radios 603-604, ENET cards 605-606,and processing circuitry 607. Radios 601-604 comprise antennas,amplifiers, filters, modulation, analog-to-digital interfaces, DSP,memory, and transceivers that are coupled over bus circuitry. Ethernetcards 605-606 comprise ports, analog-to-digital interfaces, DSP, memory,and transceivers that are coupled over bus circuitry. Processingcircuitry 607 comprises memory 608, CPU, and transceivers that arecoupled over bus circuitry. Memory 608 stores operating system 611,router application 612, network application 613, monitor application614, connection application 615, slice application 616, agentapplication 617, 5GNR application 618, WIFI application 619, ENETapplication 620, and IP application 621. The antennas in 5GNR radio 601are wirelessly coupled to 5GNR AN 411 over a 5GNR link. The antennas in5GNR radio 602 are wirelessly coupled to UE 401 over a 5GNR link. Theantennas in WIFI radio 603 are wirelessly coupled to WIFI AN 412 over aWIFI link. The antennas in WIFI radio 604 are wirelessly coupled to UE402 over a WIFI link. The port in ENET card 605 is wireline coupled toENET AN 413 over an ENET link. The port in ENET card 606 is wirelinecoupled to UE 403 over an ENET link. Transceivers in radios 601-604 andcards 605-606 are coupled to transceivers in processing circuitry 607.

The CPU in processing circuitry 607 retrieves and executes operatingsystem 611 and applications 612-621 to exchange network signaling anduser data with ANs 411-413. In particular, operating system 611 directsprocessing circuitry 608 to execute applications 612-621 in containersbased on a container configuration. The container configurationindicates CPU resources, memory resources, and transceiver resources forthe containers—and their applications. Connection application 615controls quality-of-service and priority for the data connections thatare served by network application 613 to UEs 401-403. Slice application616 controls slice information and priorities for the slices that areserved to UEs 401-403.

In some examples, some of the 5GNR, WIFI, and ENET components could beomitted. For example, the 5GNR portion for UE access could be omitted,so router 410 only serves WIFI and ENET access to UEs. The WIFI portionfor network access could be omitted, so router 410 only uses 5GNR andENET to access the network. Various combinations could be used for UEaccess and network access—including the addition of other communicationinterfaces like Bluetooth or LP-WAN.

FIG. 7 illustrates exemplary non-3GPP access nodes 422-423 in 5Gwireless communication network 400. Non-3GPP access nodes 422-423comprise examples of access node 120, although node 120 may differ. WIFIAN 422 comprises WIFI radio 701 and node circuitry 702. WIFI radio 701comprises antennas, amplifiers, filters, modulation, analog-to-digitalinterfaces, DSP, memory, and transceivers that are coupled over buscircuitry. Node circuitry 702 comprises memory, CPU, user interfaces andcomponents, and transceivers that are coupled over bus circuitry. Thememory in node circuitry 702 stores an operating system and networkapplications for IP and WIFI. The antennas in WIFI radio 701 arewirelessly coupled to UE 402 over a WIFI link. Transceivers in WIFIradio 701 are coupled to transceivers in node circuitry 702.Transceivers in node circuitry 702 are coupled to transceivers in IWF431. The CPU in node circuitry 702 executes the operating system andnetwork applications to exchange network signaling and user data with UE402 and with IWF 431.

ENET AN 412 comprises ENET card 703 and node circuitry 704. ENET card703 comprises ports, analog-to-digital interfaces, DSP, memory, andtransceivers that are coupled over bus circuitry. Node circuitry 704comprises memory, CPU, user interfaces and components, and transceiversthat are coupled over bus circuitry. The memory in node circuitry 704stores an operating system and network applications for IP and ENET. Theports in ENET card 703 are wireline coupled to UE 403 over an ENET link.Transceivers in ENET card 703 are coupled to transceivers in nodecircuitry 704. Transceivers in node circuitry 704 are coupled totransceivers in IWF 431. The CPU in node circuitry 704 executes theoperating system and network applications to exchange network signalingand user data with UE 403 and with IWF 431.

FIG. 8 illustrates exemplary 5G New Radio (5GNR) access node 421 in 5Gwireless communication network 400. 5GNR access node 421 comprises anexample of access node 120, although node 120 may differ. 5GNR accessnode 421 comprises Radio Unit (RU) 801, Distributed Unit (DU) 802, andCentralized Unit (CU) 803. RU 801 comprises 5GNR antennas, amplifiers,filters, modulation, analog-to-digital interfaces, DSP, memory, radioapplications, and transceivers that are coupled over bus circuitry. DU802 comprises memory, CPU, user interfaces and components, andtransceivers that are coupled over bus circuitry. The memory in DU 802stores operating system 804 and network applications for physical layer,media access control, and radio link control. CU 803 comprises memory,CPU, user interfaces and components, and transceivers that are coupledover bus circuitry. The memory in CU 803 stores an operating system andnetwork applications for packet data convergence protocol, service dataadaption protocol, and radio resource control. The antennas in RU 801are wirelessly coupled to UE 401 over 5GNR links. Transceivers in RU 801are coupled to transceivers in DU 802. Transceivers in DU 802 arecoupled to transceivers in CU 803. Transceivers in CU 803 are coupled toAMF 432 and UPFs 451-454. The DSP and CPU in RU 801, DU 802, and CU 803execute radio applications, operating systems, and network applicationsto exchange network signaling and user data with UE 401, AMF 432, andUPFs 451-454.

FIG. 9 illustrates exemplary network data center 430 in 5G wirelesscommunication network 400. Network data center 430 comprises an exampleof network control 131 and network slices 132, although control 131 andslices 132 may differ. Network data center 430 comprises NetworkFunction (NF) hardware 901, NF hardware drivers 902, NF operatingsystems 903, NF virtual layer 904, and NF Software (SW) 905. NF hardware901 comprises Network Interface Cards (NICs), CPU, RAM, Flash/DiskDrives (DRIVE), and Data Switches (DSW). NF hardware drivers 902comprise software that is resident in the NIC, CPU, RAM, DRIVE, and DSW.NF operating systems 903 comprise kernels, modules, and applicationsthat form containers for virtual layer and NF software execution. NFvirtual layer 904 comprises vNIC, vCPU, vRAM, vDRIVE, and vSW. NF SW 905comprises IWF SW 931, AMF SW 932, NSSF SW 933, SMF SW 934, slices441-444. Slice 441 comprises UPF SW 951 and RCF SW 955. Slice 442comprises UPF SW 952. Slice 443 comprises UPF SW 953. Slice 444comprises UPF SW 954 and ASF SW 956. Other NFs like AuthenticationServer Function (AUSF) and Network Repository Function (NRF) aretypically present but are omitted for clarity. Network data center 430may be located at a single site or be distributed across multiplegeographic locations. The NIC in NF hardware 901 are coupled to 5GNR AN421, WIFI AN 422, ENET AN 423, and external systems. NF hardware 901executes NF hardware drivers 902, NF operating systems 903, NF virtuallayer 904, and NFs 905 to form and operate IWF 431, AMF 432, NSSF 433,SMF 434, and slices 441-444.

FIG. 10 illustrates wireless router 410 and Router Control Function(RCF) 455 in wireless communication network 400. RCF 455 comprisesrouter control 1011, rules engine 1012, and QoS analytics 1013. Wirelessrouter 410 comprises operating system 611 and containers 1001-1006.Container 1001 executes router application 612 responsive to operatingsystem 611. Container 1002 executes network application 613 responsiveto operating system 611. Container 1003 executes monitor application 614responsive to operating system 611. Container 1004 executes connectionapplication 615 responsive to operating system 611. Container 1005executes slice application 616 responsive to operating system 611.Container 1006 executes agent application 617 responsive to operatingsystem 611.

Router application 612 exchanges user data with UEs 401-403 (not shownon Figure Router application 612 exchanges the user data with networkapplication 613. Network application 613 exchanges the user data withUPF SW 952-954 for slices 442-444. Monitor application 614 determinesperformance information—typically from applications 612-613—thatindicates data throughput, latency, and the like for the UE connectionsand slices. Monitor application 614 transfers the performance data toQoS analytics 1013 over network application 613 and UPF SW 951. QoSanalytics 1013 formats and processes the performance data and transfersthe analytic results to rules engine 1012. Rules engine 1012 processesthe analytic results to generate a new container configuration, sliceconfiguration, and connection configuration for router 410. For example,rules engine 1012 boosts resources, priorities, and throughputs for someslices while reducing resources, priorities, and throughputs for otherslices. Rules engine 1012 transfers the new container configuration,slice configuration, and connection configuration for router 410 torouter control 1011. Router control 1011 transfers the new containerconfiguration, slice configuration, and connection configuration toagent application 617 over UPF SW 951 and network application 613.

Agent application 617 transfers the new container configuration tooperating system 611. Operating system 611 controls the computingresources of containers 1001-1006 based on the new containerconfiguration. For example, applications 612-613 may get a resourceboost for a large uplink burst of user data. To boost a slice in router410, RCF 455 allocates container resources to the applications thatsupport the high-priority slice connections.

Agent application 617 transfers the new slice configuration to sliceapplication 616. Prior to receiving the slice configuration, sliceapplication 616 interacts with UEs 401-403 over router application 612to offer and accept requests for network slices 442-444. Sliceapplication 616 also interacts with AMF 432 over network application 613to get the slice information and establish slices 442-444. Sliceapplication 616 transfers the slice configuration to network application613. Network application 613 may create new slice connections based onthe slice configuration. Network application 613 prioritizes the activeslice connection based on the slice configuration. To boost a slice inrouter 410, RCF 455 allocates slice priority to the connections of theslice.

Agent application 617 transfers the new connection configuration toconnection application 615. Connection application 615 transfers theconnection configuration to network application 613. Network application613 applies data throughputs and latencies to individual connectionsbased on the connection configuration. Network application 613 mayprioritize connections in the same slice based on the connectionconfiguration. To boost a slice in router 410, RCF 455 allocatesconnection quality and priority to the connections for the slice.

FIG. 11 illustrates an exemplary operation of the 5G wirelesscommunication network that 400 has wireless router 410 to serve UEs401-403 over the network connections to network slices 442-444. Theoperation may differ in other examples. Router 410 transfers a slicerequest (RQ) for router slice 441 to AMF 432 over 5GNR AN 421 (AN 421 isnot shown on FIG. 11 ). AMF 432 and NSSF 433 interact to authorize slice441 for router 410. AMF 431 signals SMF 434 to serve router 410 overslice 441. SMF 434 directs UPF 451 in slice 441 to serve router 410 over5GNR AN 421. Router 410 registers with RCF 455 over AN 421 and UPF 451.RCF 455 transfers default information and configurations for container,slice, and connection to router 410 over AN 421 and UPF 451. Router 410implements the information and configurations for container, slice, andconnection to establish connections to slices 442-444 for UEs 401-403.Router 410 exchanges user data between UEs 401-403 and slices 442-444over the connections.

Router 410 transfers performance data for the connections to RCF 455over 5GNR AN 421 and UPF 451. RCF 455 processes the performanceinformation to generate and transfer new configurations for container,slice, and connection to router 410 over AN 421 and UPF 451. Router 410implements the new configurations for container, slice, and connectionto possibly modify the connections to slices 442-444 for UEs 401-403.Router 410 exchanges user data between UEs 401-403 and slices 442-444over the connections. Router 410 transfers more performance data for theconnections to RCF 455 over 5GNR AN 421 and UPF 451 and the processrepeats.

FIG. 12 illustrates an exemplary operation of the 5G wirelesscommunication network that 400 has wireless router 410 to serve UEs401-403 over the network connections to network slices 442-444. Theoperation may differ in other examples. Rules engine 1002 transfersslice information to slice application 616 over controller 1001 andapplications 613 and 617. Slice application transfers the sliceinformation to UEs 401-403 (not shown on FIG. 12 ). After establishingslice connections, router application 612 exchanges user data with UEs401-403 and exchanges the user data with network application 613.Network application 613 exchanges the user data with slices 442-444 (notshown on FIG. 12 ) based on the slice and connection configurations.

Router application 612 and network application 613 transfer performancedata like throughput and latency for the UE connections to slices442-444 to monitor application 614. Monitor application 614 transfersthe performance data to QoS analytics 1003. QoS analytics 1003 developsQoS instructions based on the performance data. Rules engine 1002translates the QoS instructions into configurations for container,slice, and connection and transfers the configurations to agentapplication 617 over router control 1001 and network application 613.Agent application 617 transfers the slice configuration to sliceapplication 616. Agent application 617 transfers the connectionconfiguration to connection application 614. Agent application 617transfers the container configuration to operating system 611. Sliceapplication 616 and connection application 615 transfer theirconfigurations to network application 613. Network application 613exchanges user data with UEs 401-403 over router application 612.Network application 613 exchanges user data with slices 442-444 based onthe configurations.

FIG. 13 illustrates an exemplary operation of the 5G wirelesscommunication network that 400 has wireless router 410 to serve UEs401-403 over the network connections to network slices 442-444. Theoperation may differ in other examples. UE 401 attaches to router 410over 5GNR AN 421. Router transfer slice information to UE 401. UE 401requests a slice from router 410. Router 410 requests the slice for UE401 from AMF 432. AMF 432 and NSSF 433 interact to authorize slice 442for UE 401. AMF 432 directs SMF 434 to serve router 410 for UE 401 overslice 442. SMF 434 signals UPF 452 to serve router 410 for UE 401 over5GNR AN 421. UE 401 and router 410 exchange user data for slice 442.Router 410 and UPF 452 exchange the user data for slice 442 based on theslice and connection configurations. UPF 452 exchanges the user data forslice 442 with external systems.

The wireless data network circuitry described above comprises computerhardware and software that form special-purpose networking circuitry toserve UEs over data routers and wireless network slices. The computerhardware comprises processing circuitry like CPUs, DSPs, GPUs,transceivers, bus circuitry, and memory. To form these computer hardwarestructures, semiconductors like silicon or germanium are positively andnegatively doped to form transistors. The doping comprises ions likeboron or phosphorus that are embedded within the semiconductor material.The transistors and other electronic structures like capacitors andresistors are arranged and metallically connected within thesemiconductor to form devices like logic circuitry and storageregisters. The logic circuitry and storage registers are arranged toform larger structures like control units, logic units, andRandom-Access Memory (RAM). In turn, the control units, logic units, andRAM are metallically connected to form CPUs, DSPs, GPUs, transceivers,bus circuitry, and memory.

In the computer hardware, the control units drive data between the RAMand the logic units, and the logic units operate on the data. Thecontrol units also drive interactions with external memory like flashdrives, disk drives, and the like. The computer hardware executesmachine-level software to control and move data by driving machine-levelinputs like voltages and currents to the control units, logic units, andRAM. The machine-level software is typically compiled from higher-levelsoftware programs. The higher-level software programs comprise operatingsystems, utilities, user applications, and the like. Both thehigher-level software programs and their compiled machine-level softwareare stored in memory and retrieved for compilation and execution. Onpower-up, the computer hardware automatically executesphysically-embedded machine-level software that drives the compilationand execution of the other computer software components which thenassert control. Due to this automated execution, the presence of thehigher-level software in memory physically changes the structure of thecomputer hardware machines into special-purpose networking circuitry toserve UEs over data routers and wireless network slices.

The above description and associated figures teach the best mode of theinvention. The following claims specify the scope of the invention. Notethat some aspects of the best mode may not fall within the scope of theinvention as specified by the claims. Those skilled in the art willappreciate that the features described above can be combined in variousways to form multiple variations of the invention. Thus, the inventionis not limited to the specific embodiments described above, but only bythe following claims and their equivalents.

What is claimed is:
 1. A method of operating a data router to serve UserEquipment (UEs) over network connections to network slices, the methodcomprising: the data router receiving a container configuration and aconnection configuration from a wireless communication network; the datarouter exchanging user data with the UEs; the data router executing dataapplications in operating system containers based on the containerconfiguration; and the data applications exchanging the user data withthe network slices over the network connections based on the connectionconfiguration.
 2. The method of claim 1 further comprising: the dataapplications generating performance information for the networkconnections; and the data router transferring the performanceinformation for the network connections to the wireless communicationnetwork.
 3. The method of claim 1 wherein the data router executing thedata applications in the operating system containers based on thecontainer configuration comprises individually controlling CentralProcessing Unit (CPU) resources used by individual ones of the operatingsystem containers.
 4. The method of claim 1 wherein the data routerexecuting the data applications in the operating system containers basedon the container configuration comprises individually controlling datamemory resources used by individual ones of the operating systemcontainers.
 5. The method of claim 1 wherein the data router exchangingthe user data with the UEs comprises exchanging the user data using anInternet Protocol (IP) and a Wireless Fidelity (WIFI) protocol.
 6. Themethod of claim 1 wherein the data router exchanging the user data withthe UEs comprises exchanging the user data using an Internet Protocol(IP) and an Ethernet protocol.
 7. The method of claim 1 wherein the datarouter exchanging the user data with the UEs comprises exchanging theuser data using an Internet Protocol (IP) and a Fifth Generation NewRadio (5GNR) protocol.
 8. The method of claim 1 wherein the dataapplications exchanging the user data over the network connectionscomprises exchanging the user data using an Internet Protocol (IP) and aWireless Fidelity (WIFI) protocol.
 9. The method of claim 1 wherein thedata applications exchanging the user data over the network connectionscomprises exchanging the user data using an Internet Protocol (IP) and aFifth Generation New Radio (5GNR) protocol.
 10. A method of operating adata router to serve User Equipment (UEs) over network connections tonetwork slices, the method comprising: a network radio receiving acontainer configuration and a connection configuration from a wirelesscommunication network; a user radio exchanging user data with the UEs;processing circuitry executing data applications in operating systemcontainers based on the container configuration; and the dataapplications exchanging the user data with the network slices over thenetwork radio and the network connections based on the connectionconfiguration.
 11. The method of claim 10 wherein the processingcircuitry executing the data applications in the operating systemcontainers based on the container configuration comprises individuallycontrolling Central Processing Unit (CPU) resources used by individualones of the operating system containers.
 12. The method of claim 10wherein the processing circuitry executing the data applications in theoperating system containers based on the container configurationcomprises individually controlling data memory resources used byindividual ones of the operating system containers.
 13. A data router toserve User Equipment (UEs) over network connections to network slices,the data router comprising: a network radio to receive a containerconfiguration and a connection configuration from a wirelesscommunication network; a user radio to exchange user data with the UEs;processing circuitry to execute data applications in operating systemcontainers based on the container configuration; and the dataapplications to exchange the user data with the network slices over thenetwork radio and the network connections based on the connectionconfiguration.
 14. The data router of claim 13 further comprising: thedata applications to generate performance information for the networkconnections; and the network radio to transfer the performanceinformation for the network connections to the wireless communicationnetwork.
 15. The data router of claim 13 wherein the processingcircuitry is to individually control Central Processing Unit (CPU)resources used by individual ones of the operating system containers toexecute the data applications in the operating system containers basedon the container configuration.
 16. The data router of claim 13 whereinthe processing circuitry is to individually control data memoryresources used by individual ones of the operating system containers toexecute the data applications in the operating system containers basedon the container configuration.
 17. The data router of claim 13 whereinthe user radio is to exchange the user data with the UEs using anInternet Protocol (IP) and a Wireless Fidelity (WIFI) protocol toexchange the user data with the UEs.
 18. The data router of claim 13wherein the user radio is to exchange the user data with the UEs usingan Internet Protocol (IP) and a Fifth Generation New Radio (5GNR)protocol to exchange the user data with the UEs.
 19. The data router ofclaim 13 wherein the data applications are to exchange the user dataover the network radio and the network connections using an InternetProtocol (IP) and a Wireless Fidelity (WIFI) protocol to exchange theuser data with the network slices over the network radio and the networkconnections.
 20. The data router of claim 13 wherein the dataapplications are to exchange the user data over the network radio andthe network connections using an Internet Protocol (IP) and a FifthGeneration New Radio (5GNR) protocol to exchange the user data with thenetwork slices over the network radio and the network connections.